Skip to content

docs: drop dead wzrd.in standalone browser build link - #1052

Open
JiuYue0820 wants to merge 2 commits into
debug-js:masterfrom
JiuYue0820:docs/fix-wzrd-standalone-build-link
Open

JiuYue0820 wants to merge 2 commits into
debug-js:masterfrom
JiuYue0820:docs/fix-wzrd-standalone-build-link

Conversation

@JiuYue0820

@JiuYue0820 JiuYue0820 commented Aug 17, 2026

Copy link
Copy Markdown

Problem

https://wzrd.in/standalone/debug@latest now returns HTTP 404 on GET. The README still advertised that hosted browserify-as-a-service build.

https://github.com/substack/node-browserify still works, but the project lives at https://github.com/browserify/browserify.

Change

  • Remove the dead wzrd.in standalone-build promise.
  • Keep the local browserify instructions and point that repo at its current org URL.

Verified with curl -L GET on 2026-08-17:

  • https://wzrd.in/standalone/debug@latest -> 404
  • https://github.com/browserify/browserify -> 200

wzrd.in/standalone/debug@latest now 404s. Point the browser build at jsDelivr and the browserify repo at its current home.

Co-authored-by: FirmamentalSpring <287222957+FirmaSpring@users.noreply.github.com>
wzrd.in/standalone/debug@latest now returns 404 on GET, so the README no longer promised a working hosted browserify build. Keep the local browserify instructions and point the browserify repo at its current org URL.

Co-authored-by: FirmamentalSpring <287222957+FirmaSpring@users.noreply.github.com>
@JiuYue0820 JiuYue0820 changed the title docs: replace dead wzrd.in standalone build with jsDelivr docs: drop dead wzrd.in standalone browser build link Aug 17, 2026

@lbesecker195 lbesecker195 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked the links: https://wzrd.in/standalone/debug@latest returns 404 (the wzrd.in landing page still loads, but the standalone builds it generates don't), and github.com/substack/node-browserify redirects to github.com/browserify/browserify, so pointing at the canonical repo and dropping the build-as-a-service line is right. LGTM.

@Qix-

Qix- commented Sep 14, 2026

Copy link
Copy Markdown
Member

The whiplash I got from hovering over the "report" button after reading "drop dead" is indescribable :D unfortunately not the first death threat I would have gotten over this package.

Anyway, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants